Skip to content

Conversation

@Christoffer-JL
Copy link

@Christoffer-JL Christoffer-JL commented Nov 28, 2025

aten::view_copy is now considered no-compute by
the partitioner. This prevents the case
where a partition is left empty if two
view_copy ops cancels each other out,
leaving the partition empty.

This was the case when running
torch_audio_hdemucs_high_musdb(_plus),
which made Vela output an error.

Additionaly, some incorrectly named tests in test_sum have been renamed from view to sum

cc @freddan80 @per @zingo @oscarandersson8218 @digantdesai

aten::view_copy is now considered no-compute by
the partitioner. This prevents the case
where a partition is left empty if two
view_copy ops cancels each other out,
leaving the partition empty.

This was the case when running
torch_audio_hdemucs_high_musdb(_plus),
which made Vela output an error.

Additionaly, some incorrectly named tests in test_sum have
been renamed from view to sum

JIRA: MLETORCH-1535

Change-Id: I1fe5175fd560486a064258dee5f0048836022ee1
@pytorch-bot
Copy link

pytorch-bot bot commented Nov 28, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16005

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure

As of commit a5e2d2c with merge base e38734e (image):

NEW FAILURE - The following job has failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla
Copy link

meta-cla bot commented Nov 28, 2025

Hi @Christoffer-JL!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@Christoffer-JL Christoffer-JL marked this pull request as draft November 28, 2025 10:24
@Christoffer-JL Christoffer-JL marked this pull request as ready for review November 28, 2025 10:24
@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Dec 1, 2025
@meta-cla
Copy link

meta-cla bot commented Dec 1, 2025

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@pytorch-bot
Copy link

pytorch-bot bot commented Dec 2, 2025

To add the ciflow label ciflow/trunk please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

@pytorch-bot pytorch-bot bot removed the ciflow/trunk label Dec 2, 2025
@Erik-Lundell Erik-Lundell added partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm ciflow/trunk labels Dec 2, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 2, 2025

To add the ciflow label ciflow/trunk please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

@pytorch-bot pytorch-bot bot removed the ciflow/trunk label Dec 2, 2025
@Erik-Lundell Erik-Lundell added ciflow/trunk release notes: none Do not include this in the release notes labels Dec 2, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 2, 2025

To add the ciflow label ciflow/trunk please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

@pytorch-bot pytorch-bot bot removed the ciflow/trunk label Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm release notes: none Do not include this in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants